Skip to content

Updates for 0.39.0-rc.2 #4770

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Conversation

weave-gitops-bot
Copy link
Collaborator

⚠️ Breaking changes

Describe any breaking changes here, or delete this block

✍️ Action required

Describe any user facing actions here, or delete this block.

💸 Features and improvements

Describe any user facing changes here, or delete this block.

Examples of user facing changes:

  • API changes
  • Bug fixes
  • Any changes in behaviour
  • Changes requiring upgrade notices or deprecation warning

Flux compatibility

Flux version Minimum required
v2.4 >= 2.4.0

For Flux migrations to v2.0 see flux or weave gitops documentation.

Uncategorized

@weave-gitops-bot
Copy link
Collaborator Author

To change the release notes, edit the pull request description.

As soon as you approve the PR, the release will start, and will be automatically merged when finished

Copy link
Contributor

Hey there and thank you for opening this pull request! 👋

We require pull request titles to follow the
Conventional Commits specification
and it looks like your proposed title needs to be adjusted.

While the specification does not require a specific casing, it recommends being consistent.
We use the pull request title in automated release changelog updates, and would like our
changelogs to look nice.

Details:

No release type found in pull request title "Updates for 0.39.0-rc.2". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@casibbald
Copy link
Collaborator

broken pr commit message

@casibbald casibbald closed this Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants